Format consistency

Characteristic Name:	Format consistency
Dimension:	Consistency
Description:	Data formats are consistently used
Granularity:	Element
Implementation Type:	Rule-based approach
Characteristic Type:	Declarative

Verification Metric:

The number of inconsistent data formats reported in an attribute per thousand records

GuidelinesExamplesDefinitons

The implementation guidelines are guidelines to follow in regard to the characteristic. The scenarios are examples of the implementation

Guidelines:	Scenario:
Maintain consistent formats for data values across different data bases and different tables in the same database.	(1) Telephone number : Country code/Area code/number (2) Address : House number, Street, Suburb, Sate, Country
Maintain structural similarity or compatibility of entities and attributes across systems (databases/data sets) and across time.	(1) Customer record has the same structure in all systems which it is being used.
Maintain consistent and compatible encoding /decoding standards across different applications.	(1) ASCII, UTF-8, XML

Validation Metric:

How mature is the creation and implementation of the DQ rules to maintain format consistency

These are examples of how the characteristic might occur in a database.

Example:	Source:
1) Each class in a UK secondary school is allocated a class identifier; this consists of the 3 initials of the teacher plus a two digit year group number of the class. It is declared as AAA99 (3 Alpha characters and two numeric characters). 2) A new year 9 teacher, Sally Hearn (without a middle name) is appointed therefore there are only two initials. A decision must be made as to how to represent two initials or the rule will fail and the database will reject the class identifier of “SH09”. It is decided that an additional character “Z” will be added to pad the letters to 3: “SZH09”, however this could break the accuracy rule. A better solution would be to amend the database to accept 2 or 3 initials and 1 or 2 numbers. 3) In this scenario, the parent, a US Citizen, applying to a European school completes the Date of Birth (D.O.B) on the application form in the US date format, MM/DD/YYYY rather than the European DD/MM/YYYY format, causing the representation of days and months to be reversed.	N. Askham, et al., “The Six Primary Dimensions for Data Quality Assessment: Defining Data Quality Dimensions”, DAMA UK Working Group, 2013.
if a data element is used to store the color of a person’s eyes, a value of TRUCK is invalid. A value of BROWN for my eye color would be valid but inaccurate, in that my real eye color is blue.	J. E. Olson, “Data Quality: The Accuracy Dimension”, Morgan Kaufmann Publishers, 9 January 2003.

Example:

Source:

1) Each class in a UK secondary school is allocated a class identifier; this consists of the 3 initials of the teacher plus a two digit year group number of the class. It is declared as AAA99 (3 Alpha characters and two numeric characters).

2) A new year 9 teacher, Sally Hearn (without a middle name) is appointed therefore there are only two initials. A decision must be made as to how to represent two initials or the rule will fail and the database will reject the class identifier of “SH09”. It is decided that an additional character “Z” will be added to pad the letters to 3: “SZH09”, however this could break the accuracy rule. A better solution would be to amend the database to accept 2 or 3 initials and 1 or 2 numbers.

3) In this scenario, the parent, a US Citizen, applying to a European school completes the Date of Birth (D.O.B) on the application form in the US date format, MM/DD/YYYY rather than the European DD/MM/YYYY format, causing the representation of days and months to be reversed.

N. Askham, et al., “The Six Primary Dimensions for Data Quality Assessment: Defining Data Quality Dimensions”, DAMA UK Working Group, 2013.

if a data element is used to store the color of a person’s eyes, a value of TRUCK is invalid. A value of BROWN for my eye color would be valid but inaccurate, in that my real eye color is blue.

J. E. Olson, “Data Quality: The Accuracy Dimension”, Morgan Kaufmann Publishers, 9 January 2003.

The Definitions are examples of the characteristic that appear in the sources provided.

Definition:	Source:
A measure of the equivalence of information stored or used in various data stores, applications, and systems, and the processes for making data equivalent	D. McGilvray, “Executing Data Quality Projects: Ten Steps to Quality Data and Trusted Information”, Morgan Kaufmann Publishers, 2008.
The extent to which similar attributes or elements of an information object are consistently represented using the same structure, format, and precision.	STVILIA, B., GASSER, L., TWIDALE, M. B. & SMITH, L. C. 2007. A framework for information quality assessment. Journal of the American Society for Information Science and Technology, 58, 1720-1733.

Data maintenance

Characteristic Name:	Data maintenance
Dimension:	Availability and Accessability
Description:	Data should be accessible to perform necessary updates and maintenance operations in it’s entirely
Granularity:	Record
Implementation Type:	Process-based approach
Characteristic Type:	Usage

Verification Metric:

The number of tasks failed or under performed due to lack of data maintenance

The number of complaints received due to lack of continuity in data access

GuidelinesExamplesDefinitons

The implementation guidelines are guidelines to follow in regard to the characteristic. The scenarios are examples of the implementation

Guidelines:	Scenario:
Technological changes in the infrastructure/system should be handled in such a way that they should not make data inaccessible	(1) Sales order is created once a customer signs a contract. Then it is updated in three instances 1)Delivery date and shipment date is updated once the production plan is created. 2) Actual quantity is updated once the manufacturing is complete 3) Total cost is updated once the freight changes are incurred. A sales order is achieved after one years from delivery.
A maintenance policy for mission critical data should be developed and implemented to handle on going systematic updates (Create, read, update, delete, archive and cleanse)	(1) Customer data : Created when a customer enters into a contract, updated once the customer details change or contact change, archived once the contact end
When multiple versions of the same data is available through different datasets\databases create a master record and make it available across the systems	(1) Master data management
Leverage application and storage technology in such a way that the maintenance policies can be applied on data	(1)Addresses which were not updated during the last 24 months are prompted for validations
Create a responsibility structure/Authorisation structure and a communication structure to manage the process of information generation maintenance and utilisation	(1) It is the responsibility of the work study team to provide SMV (standard minute values) for a garment. (2) Approved SMVs should be sent to the planning department for planning purposes.

Validation Metric:

How mature is the data maintenance process

These are examples of how the characteristic might occur in a database.

Example:	Source:
minutes of a meeting will be produced in draft form and reviewed by the members of the committee before being approved. Once this process of creation is ﬁnished the record must be ﬁxed and must not be susceptible to change. If a record is changed or manipulated in some way, it no longer provides evidence of the transaction it originally documented. For example, if someone alters the minutes of a meeting after they have been approved, the minutes can no longer be considered an accurate record of the meeting. This is another issue that becomes more important in an electronic context.	K. Smith, “Public Sector Records Management: A Practical Guide”, Ashgate, 2007.

Example:

Source:

minutes of a meeting will be produced in draft form and reviewed by the members of the committee before being approved. Once this process of creation is ﬁnished the record must be ﬁxed and must not be susceptible to change. If a record is changed or manipulated in some way, it no longer provides evidence of the transaction it originally documented. For example, if someone alters the minutes of a meeting after they have been approved, the minutes can no longer be considered an accurate record of the meeting. This is another issue that becomes more important in an electronic context.

K. Smith, “Public Sector Records Management: A Practical Guide”, Ashgate, 2007.

The Definitions are examples of the characteristic that appear in the sources provided.

Definition:	Source:
A measure of the degree to which data can be accessed and used and the degree to which data can be updated, maintained, and managed.	D. McGilvray, “Executing Data Quality Projects: Ten Steps to Quality Data and Trusted Information”, Morgan Kaufmann Publishers, 2008.
Can all of the information be organized and updated on an on-going basis?	EPPLER, M. J. 2006. Managing information quality: increasing the value of information in knowledge-intensive products and processes, Springer.